Providing remote interactions with host device using a wireless device

ABSTRACT

A wearable device that communicates with a host device can be used to initiate a communication functionality of the host device (e.g., telephone calls, text messages). The wearable device can obtain user input indicating a recipient of the communication and in some instances content for the communication and can provide an instruction to the host device. The host device can use the indicated recipient and content to initiate communication and where applicable to send the content. Recipients and/or content can be selected from predefined lists available on the wearable device.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 14/774,664, filing date of Mar. 14, 2014, entitled “ProvidingRemote Interactions with Host Device Using a Wireless Device,” whichclaims the benefit of International Application No. PCT/US2013/032498,filing date of Mar. 15, 2013, entitled “Providing Remote Interactionswith Host Device Using a Wireless Device”. The disclosures of which areincorporated herein by reference in their entirety.

BACKGROUND

The present disclosure relates generally to wireless electronic devicesand in particular to providing remote interactions with a host deviceusing a wireless device.

Mobile electronic devices, such as mobile phones, smart phones, tabletcomputers, media players, and the like, have become quite popular. Manyusers carry a device almost everywhere they go and use their devices fora variety of purposes, including making and receiving phone calls,sending and receiving text messages and emails, navigation (e.g., usingmaps and/or a GPS receiver), purchasing items in stores (e.g., usingcontactless payment systems), and/or accessing the Internet (e.g., tolook up information).

However, a user's mobile device is not always readily accessible. Forinstance, when a mobile device receives a phone call, the device may bein a user's bag or pocket, and the user may be walking, driving,carrying something, or involved in other activity that makes itinconvenient or impossible for the user to reach into the bag or pocketto find the device.

SUMMARY

Certain embodiments of the present invention relate to wearableelectronic devices that can be connected (e.g., via wireless pairing)with another device (referred to herein as a “host device”), such as asmart phone, other mobile phone, tablet computer, media player, laptopcomputer, or the like. When paired, the wearable device can provideaccess to various functionalities of the host device.

In some embodiments, a wearable device can be operated by a user torespond to an event notification generated by a host device. Thewearable device can receive a notification of the event from the hostdevice and present the user with an alert and a prompt to respond. Ifthe user responds to the prompt, the wearable device can transmit theresponse to the host device. For example, a user can respond to a phonecall, text message, or other communication received at the host device.

In some embodiments, a wearable device can be operated by a user toinitiate a functionality of a host device, independently of any priorevent notification. For example, the wearable device can present a userinterface via which the user can select a functionality to be invokedand further interfaces to control that functionality. Accordingly, auser can operate a wearable device to provide a phone number andinstruct a host device to place a phone call to that number, or a usercan operate a wearable device to send a text message to a specifiedrecipient, or a user can operate a wearable device to control mediaplayback and/or any other functionality available on a particular hostdevice.

Certain embodiments of the invention relate to placing a phone callusing a wearable device that communicates with a host device having atelephone transceiver. In some embodiments, a wearable device can obtainuser input indicative of a call to be placed, including identifier of arecipient of the call. For example, the wearable device can present tothe user a list of the user's contacts and can receive a user inputselecting one of the contacts from the list as the recipient. As anotherexample, the wearable device can present to the user a virtual keypad,which the user can operate to enter a phone number to be called. Thewearable device can send an instruction to the host device to place aphone call and provide the identifier of the recipient. The host devicecan place the call. In some embodiments, e.g., where the recipient isidentified as a contact, the host device can perform a lookup operationto determine a phone number associated with the contact, then place thecall to that phone number. Once the call as been placed, the host devicecan send confirmation to the wearable device. In response to receivingthe confirmation, the wearable device can present a control operable bythe user to terminate the call.

While the call is in progress, the host device can route audio signalsassociated with the call between the telephone transceiver and an audiodevice, and the routing can be based at least in part on a userpreference setting of the host device. For instance, the host device canroute a call-related audio output signal received at the telephonetransceiver to the wearable device, which can deliver the signal to aspeaker (which can be part of the wearable device or a separate device).As another example, the wearable device can also obtain a call-relatedaudio input signal from a microphone (which can be part of the wearabledevice or a separate device) and can send the call-related audio inputsignal to the host device, which can route the signal to the telephonetransceiver. In other embodiments, the host device can routecall-related audio input and/or call-related audio output from and/or toaudio devices other than the wearable device.

In some embodiments, a call can continue until it is terminated. Forexample, the wearable device can detect user operation of the controloperable to end the call and can send a notification to the host devicethat the call should be ended. As another example, the wearable devicecan receive a notification from the host device that the call has ended(e.g., because the recipient terminated the call) and can present analert to the user indicating that the call has ended.

Certain embodiments of the invention relate to sending a message (suchas a text message) using a wearable device that communicates with a hostdevice having a telecommunication interface. In some embodiments, thewearable device can obtain user input indicative of a recipient of amessage and further user input indicative of content of the message. Forexample, the wearable device can present to the user a list of theuser's contacts and can receive a user input selecting one of thecontacts from the list as the recipient. The wearable device can alsopresent to the user a list of predefined messages and can receive a userinput selecting one of the messages from the list as the messagecontent. The wearable device can send an instruction to the host deviceto send the message, and the instruction can include an identifier ofthe recipient and an indication of the content of the message. Inresponse to the instruction, the host can create a message based on theprovided indication of content. For example, if the content indicationprovides an identifier of a message selected from a list, the hostdevice can perform a lookup operation to obtain corresponding messagecontent and include that content in the message. The host device cansend the message to a destination address determined based on therecipient identifier. The host can send a confirmation to the wearabledevice that the message has been sent, and the wearable device can soinform the user.

Certain embodiments relate to facilitating user operation of a wearabledevice, e.g., by automatically activating a user interface of thewearable device in response to an event indicating that a user is likelyto begin using the wearable device. For example, the wearable device canhave a motion sensor that it can use to detect a motion characteristicof a user moving the wearable device into a viewing position. In thecase of a wrist-worn device, for instance, the characteristic motion cancorrespond to a motion that moves the user's wrist into the user's lineof sight. In response to detecting this motion, the wearable device canactivate a user interface component such as a display, a touch sensor, atouchscreen interface (which can include a display and a touch sensor),a microphone, or the like. Other components of the wearable device canbe automatically activated based on motion detection as well. In someembodiments, the wearable device can also detect whether it is beingworn, and motion detection to trigger automatic activation can belimited to instances where the device is being worn.

The following detailed description together with the accompanyingdrawings will provide a better understanding of the nature andadvantages of the present invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a wearable device communicating wirelessly with a hostdevice according to an embodiment of the present invention.

FIG. 2 is a simplified block diagram of a wearable device according toan embodiment of the present invention.

FIGS. 3A and 3B illustrate a user operating a wearable device accordingto an embodiment of the present invention

FIG. 4 is a flow diagram of a process for responding to an eventnotification according to an embodiment of the present invention.

FIG. 5 illustrates an interface for alerting a user according to anembodiment of the present invention.

FIG. 6 illustrates another interface for alerting a user according to anembodiment of the present invention.

FIG. 7 illustrates a user interface for selecting a predefined messageaccording to an embodiment of the present invention.

FIG. 8 is a flow diagram of a process for generating an eventnotification and receiving a response according to an embodiment of thepresent invention

FIG. 9 is a flow diagram of a process for initiating a phone-callfunctionality of a host device according to an embodiment of the presentinvention.

FIG. 10 illustrates a function-selection user interface according to anembodiment of the present invention.

FIG. 11 illustrates a user interface for placing a call according to anembodiment of the present invention.

FIG. 12 illustrates a keypad user interface according to an embodimentof the present invention.

FIG. 13 illustrates a contacts user interface according to an embodimentof the present invention.

FIG. 14 is a flow diagram of a process for placing a call using awearable device according to an embodiment of the present invention.

FIG. 15 is a flow diagram of a process for sending a text message usinga wearable device according to an embodiment of the present invention.

FIG. 16 illustrates a user interface for selecting a predefined messageaccording to an embodiment of the present invention.

DETAILED DESCRIPTION

Certain embodiments of the present invention relate to wearableelectronic devices that can be connected (e.g., via wireless pairing)with another device (referred to herein as a “host device”), such as asmart phone, other mobile phone, tablet computer, media player, laptopcomputer, or the like. When paired, the wearable device can provideaccess to various functionality of the host device.

In some embodiments, a wearable device can be operated by a user torespond to an event notification generated by a host device. Thewearable device can receive a notification of the event from the hostdevice and present the user with an alert and a prompt to respond. Ifthe user responds to the prompt, the wearable device can transmit theresponse to the host device. For example, a user can respond to a phonecall, text message, or other communication received at the host device.

In some embodiments, a wearable device can be operated by a user toinitiate a functionality of a host device, independently of any priorevent notification. For example, the wearable device can present a userinterface via which the user can select a functionality to be invokedand further interfaces to control that functionality. Accordingly, auser can operate a wearable device to provide a phone number andinstruct a host device to place a phone call to that number, or a usercan operate a wearable device to send a text message to a specifiedrecipient, or a user can operate a wearable device to control mediaplayback and/or any other functionality available on a particular hostdevice.

FIG. 1 shows a wearable device 100 communicating wirelessly with a hostdevice 102 according to an embodiment of the present invention. In thisexample, wearable device 100 is shown as a wristwatch-like device with aface portion 104 connected to straps 106 a, 106 b.

Face portion 104 can include, e.g., a touchscreen display 105 that canbe appropriately sized depending on where on a user's person wearabledevice 100 is intended to be worn. A user can view information presentedby wearable device 100 on touchscreen display 105 and provide input towearable device 100 by touching touchscreen display 105. In someembodiments, touchscreen display 105 can occupy most or all of the frontsurface of face portion 104.

Straps 106 a, 106 b can be provided to allow device 100 to be removablyworn by a user, e.g., around the user's wrist. In some embodiments,straps 106 a, 106 b can be made of any flexible material (e.g., fabrics,flexible plastics, leather, chains or flexibly interleaved plates orlinks made of metal or other rigid materials) and can be connected toface portion 104, e.g., by hinges. Alternatively, straps 106 a, 106 bcan be made of a rigid material, with one or more hinges positioned atthe junction of face 104 and proximal ends 112 a, 112 b of straps 106 a,106 b and/or elsewhere along the lengths of straps 106 a, 106 b to allowa user to put on and take off wearable device 100. Different portions ofstraps 106 a, 106 b can be made of different materials; for instance,flexible or expandable sections can alternate with rigid sections. Insome embodiments, one or both of straps 106 a, 106 b can includeremovable sections, allowing wearable device 100 to be resized toaccommodate a particular user's wrist size. In some embodiments, straps106 a, 106 b can be portions of a continuous strap member that runsbehind or through face portion 104. Face portion 104 can be detachablefrom straps 106 a, 106 b; permanently attached to straps 106 a, 106 b;or integrally formed with straps 106 a, 106 b.

The distal ends of straps 106 a, 106 b opposite face portion 104 canprovide complementary clasp members 108 a, 108 b that can be engagedwith each other to secure the distal ends of straps 106 a, 106 b to eachother, forming a closed loop. In this manner, device 100 can be securedto a user's person, e.g., around the user's wrist; clasp members 108 a,108 b can be subsequently disengaged to facilitate removal of device 100from the user's person. The design of clasp members 108 a, 108 b can bevaried; in various embodiments, clasp members 108 a, 108 b can includebuckles, magnetic clasps, mechanical clasps, snap closures, etc. In someembodiments, one or both of clasp members 108 a, 108 b can be movablealong at least a portion of the length of corresponding strap 106 a, 106b, allowing wearable device 100 to be resized to accommodate aparticular user's wrist size.

Straps 106 a, 106 b can be two distinct segments, or they can be formedas a continuous band of an elastic material (including, e.g., elasticfabrics, expandable metal links, or a combination of elastic andinelastic sections), allowing wearable device 100 to be put on and takenoff by stretching a band formed straps 106 a, 106 b. In suchembodiments, clasp members 108 a, 108 b can be omitted.

Straps 106 a, 106 b and/or clasp members 108 a, 108 b can includesensors that allow wearable device 100 to determine whether it is beingworn at any given time. Wearable device 100 can operate differentlydepending on whether it is currently being worn or not. For example,wearable device 100 can inactivate various user interface and/or RFinterface components when it is not being worn. In addition, in someembodiments, wearable device 100 can notify host device 102 when a userputs on or takes off wearable device 100.

Host device 102 can be any device that communicates with wearable device100. In FIG. 1, host device 102 is shown as a smart phone; however,other host devices can be substituted, such as a tablet computer, amedia player, any type of mobile phone, a laptop or desktop computer, orthe like. Other examples of host devices can include point-of-saleterminals, security systems, environmental control systems, and so on.Host device 102 can communicate wirelessly with wearable device 100,e.g., using protocols such as Bluetooth or Wi-Fi. In some embodiments,wearable device 100 can include an electrical connector 110 that can beused to provide a wired connection to host device 102 and/or to otherdevices, e.g., by using suitable cables. For example, connector 110 canbe used to connect to a power supply to charge an onboard battery ofwearable device 100.

In some embodiments, wearable device 100 and host device 102 caninteroperate to enhance functionality available on host device 102. Forexample, wearable device 100 and host device 102 can establish a pairingusing a wireless communication technology such as Bluetooth. While thedevices are paired, host device 102 can send notifications of selectedevents (e.g., receiving a phone call, text message, or email message) towearable device 100, and wearable device 100 can present correspondingalerts to the user. Wearable device 100 can also provide an inputinterface via which a user can respond to an alert (e.g., to answer aphone call or reply to a text message). In some embodiments, wearabledevice 100 can also provide a user interface that allows a user toinitiate an action on host device 102, such as placing a phone call,sending a text message, or controlling media playback operations of hostdevice 102. Techniques described herein can be adapted to allow a widerange of host device functions to be enhanced by providing an interfacevia wearable device 100.

It will be appreciated that wearable device 100 and host device 102 areillustrative and that variations and modifications are possible. Forexample, wearable device 100 can be implemented in any wearable article,including a watch, a bracelet, a necklace, a ring, a belt, a jacket, orthe like. In some instances, wearable device 100 can be a clip-on deviceor pin-on device that has a clip or pin portion that attaches to theuser's clothing. The interface portion (including, e.g., touchscreendisplay 105) can be attached to the clip or pin portion by a retractablecord, and a user can easily pull touchscreen display 105 into view foruse without removing the clip or pin portion, then let go to returnwearable device 100 to its resting location. Thus, a user can weardevice 100 in any convenient location.

Wearable device 100 can be implemented using electronic componentsdisposed within face portion 104, straps 106 a, 106 b, and/or claspmembers 108 a, 108 b. FIG. 2 is a simplified block diagram of a wearabledevice 200 (e.g., implementing wearable device 100) according to anembodiment of the present invention. Wearable device 200 can includeprocessing subsystem 202, storage subsystem 204, user interface 206, RFinterface 208, connector interface 210, power subsystem 212,environmental sensors 214, and strap sensors 216. Wearable device 200can also include other components (not explicitly shown).

Storage subsystem 204 can be implemented, e.g., using magnetic storagemedia, flash memory, other semiconductor memory (e.g., DRAM, SRAM), orany other non-transitory storage medium, or a combination of media, andcan include volatile and/or non-volatile media. In some embodiments,storage subsystem 204 can store media items such as audio files, videofiles, image or artwork files; information about a user's contacts(names, addresses, phone numbers, etc.); information about a user'sscheduled appointments and events; notes; and/or other types ofinformation, examples of which are described below. In some embodiments,storage subsystem 204 can also store one or more application programs tobe executed by processing subsystem 210 (e.g., video game programs,personal information management programs, media playback programs,interface programs associated with particular host devices and/or hostdevice functionalities, etc.).

User interface 206 can include any combination of input and outputdevices. A user can operate input devices of user interface 206 toinvoke the functionality of wearable device 200 and can view, hear,and/or otherwise experience output from wearable device 200 via outputdevices of user interface 206.

Examples of output devices include display 220, speakers 222, and hapticoutput generator 224. Display 220 can be implemented using compactdisplay technologies, e.g., LCD (liquid crystal display), LED(light-emitting diode), OLED (organic light-emitting diode), or thelike. In some embodiments, display 220 can incorporate a flexibledisplay element or curved-glass display element, allowing wearabledevice 200 to conform to a desired shape. One or more speakers 222 canbe provided using small-form-factor speaker technologies, including anytechnology capable of converting electronic signals into audible soundwaves. In some embodiments, speakers 222 can be used to produce tones(e.g., beeping or ringing) and can but need not be capable ofreproducing sounds such as speech or music with any particular degree offidelity. Haptic output generator 224 can be, e.g., a device thatconverts electronic signals into vibrations; in some embodiments, thevibrations can be strong enough to be felt by a user wearing wearabledevice 200 but not so strong as to produce distinct sounds.

Examples of input devices include microphone 226, touch sensor 228, andcamera 229. Microphone 226 can include any device that converts soundwaves into electronic signals. In some embodiments, microphone 226 canbe sufficiently sensitive to provide a representation of specific wordsspoken by a user; in other embodiments, microphone 226 can be usable toprovide indications of general ambient sound levels without necessarilyproviding a high-quality electronic representation of specific sounds.

Touch sensor 228 can include, e.g., a capacitive sensor array with theability to localize contacts to a particular point or region on thesurface of the sensor and in some instances, the ability to distinguishmultiple simultaneous contacts. In some embodiments, touch sensor 228can be overlaid over display 220 to provide a touchscreen interface(e.g., touchscreen interface 105 of FIG. 1), and processing subsystem202 can translate touch events (including taps and/or other gesturesmade with one or more contacts) into specific user inputs depending onwhat is currently displayed on display 220.

Camera 229 can include, e.g., a compact digital camera that includes animage sensor such as a CMOS sensor and optical components (e.g. lenses)arranged to focus an image onto the image sensor, along with controllogic operable to use the imaging components to capture and store stilland/or video images. Images can be stored, e.g., in storage subsystem204 and/or transmitted by wearable device 200 to other devices forstorage. Depending on implementation, the optical components can providefixed focal distance or variable focal distance; in the latter case,autofocus can be provided. In some embodiments, camera 229 can bedisposed along an edge of face member 104 of FIG. 1, e.g., the top edge,and oriented to allow a user to capture images of nearby objects in theenvironment such as a bar code or QR code. In other embodiments, camera229 can be disposed on the front surface of face member 104, e.g., tocapture images of the user. Zero, one, or more cameras can be provided,depending on implementation.

In some embodiments, user interface 206 can provide output to and/orreceive input from an auxiliary device such as a headset. For example,audio jack 230 can connect via an audio cable (e.g., a standard 2.5-mmor 3.5-mm audio cable) to an auxiliary device. Audio jack 230 caninclude input and/or output paths. Accordingly, audio jack 230 canprovide audio to the auxiliary device and/or receive audio from theauxiliary device. In some embodiments, a wireless connection interfacecan be used to communicate with an auxiliary device.

Processing subsystem 202 can be implemented as one or more integratedcircuits, e.g., one or more single-core or multi-core microprocessors ormicrocontrollers, examples of which are known in the art. In operation,processing system 202 can control the operation of wearable device 200.In various embodiments, processing subsystem 202 can execute a varietyof programs in response to program code and can maintain multipleconcurrently executing programs or processes. At any given time, some orall of the program code to be executed can be resident in processingsubsystem 210 and/or in storage media such as storage subsystem 204.

Through suitable programming, processing subsystem 202 can providevarious functionality for wearable device 200. For example, in someembodiments, processing subsystem 202 can execute an operating system(OS) 232 and various applications for interfacing with a host device,such as a phone-interface application 234, a text-interface application236, and/or a media interface application 238. In some embodiments, someor all of these application programs can interact with a host device,e.g., by generating messages to be sent to the host device and/or byreceiving and interpreting messages from the host device. In someembodiments, some or all of the application programs can operate locallyto wearable device 200. For example, if wearable device 200 has a localmedia library stored in storage subsystem 204, media interfaceapplication 238 can provide a user interface to select and play locallystored media items. Examples of interface applications are describedbelow.

RF (radio frequency) interface 208 can allow wearable device 200 tocommunicate wirelessly with various host devices. RF interface 208 caninclude RF transceiver components such as an antenna and supportingcircuitry to enable data communication over a wireless medium, e.g.,using Wi-Fi (IEEE 802.11 family standards), Bluetooth® (a family ofstandards promulgated by Bluetooth SIG, Inc.), or other protocols forwireless data communication. RF interface 208 can be implemented using acombination of hardware (e.g., driver circuits, antennas,modulators/demodulators, encoders/decoders, and other analog and/ordigital signal processing circuits) and software components. In someembodiments, RF interface 208 can provide near-field communication(“NFC”) capability, e.g., implementing the ISO/IEC 18092 standards orthe like; NFC can support wireless data exchange between devices over avery short range (e.g., 20 centimeters or less). Multiple differentwireless communication protocols and associated hardware can beincorporated into RF interface 208.

Connector interface 210 can allow wearable device 200 to communicatewith various host devices via a wired communication path, e.g., usingUniversal Serial Bus (USB), universal asynchronous receiver/transmitter(UART), or other protocols for wired data communication. In someembodiments, connector interface 210 can provide a power port, allowingwearable device 200 to receive power, e.g., to charge an internalbattery. For example, connector interface 210 can include a connectorsuch as a mini-USB connector or a custom connector, as well assupporting circuitry. In some embodiments, the connector can be a customconnector that provides dedicated power and ground contacts, as well asdigital data contacts that can be used to implement differentcommunication technologies in parallel; for instance, two pins can beassigned as USB data pins (D+ and D−) and two other pins can be assignedas serial transmit/receive pins (e.g., implementing a UART interface).The assignment of pins to particular communication technologies can behardwired or negotiated while the connection is being established. Insome embodiments, the connector can also provide connections for audioand/or video signals, which may be transmitted to or from host device202 in analog and/or digital formats.

In some embodiments, connector interface 210 and/or RF interface 208 canbe used to support synchronization operations in which data istransferred from a host device to wearable device 200 (or vice versa).For example, as described below, a user can customize certaininformation for wearable device 200 (e.g., a “favorite” contacts listand/or specific predefined text messages that can be sent). While userinterface 206 can support data-entry operations, a user may find it moreconvenient to define customized information on a separate device (e.g.,a tablet or smartphone) that has a larger interface (e.g., including areal or virtual alphanumeric keyboard), then transfer the customizedinformation to wearable device 200 via a synchronization operation.Synchronization operations can also be used to load and/or update othertypes of data in storage subsystem 204, such as media items, applicationprograms, and/or operating system programs. Synchronization operationscan be performed in response to an explicit user request and/orautomatically, e.g., when wireless device 200 resumes communication witha particular host device or in response to either device receiving anupdate to its copy of synchronized information.

Environmental sensors 214 can include various electronic, mechanical,electromechanical, optical, or other devices that provide informationrelated to external conditions around wearable device 200. Sensors 214in some embodiments can provide digital signals to processing subsystem202, e.g., on a streaming basis or in response to polling by processingsubsystem 202 as desired. Any type and combination of environmentalsensors can be used; shown by way of example are accelerometer 242, amagnetometer 244, a gyroscope 246, and a GPS receiver 248.

Some environmental sensors can provide information about the locationand/or motion of wearable device 200. For example, accelerometer 242 cansense acceleration (relative to freefall) along one or more axes, e.g.,using piezoelectric or other components in conjunction with associatedelectronics to produce a signal. Magnetometer 244 can sense an ambientmagnetic field (e.g., Earth's magnetic field) and generate acorresponding electrical signal, which can be interpreted as a compassdirection. Gyroscopic sensor 246 can sense rotational motion in one ormore directions, e.g., using one or more MEMS (micro-electro-mechanicalsystems) gyroscopes and related control and sensing circuitry. GlobalPositioning System (GPS) receiver 248 can determine location based onsignals received from GPS satellites.

Other sensors can also be included in addition to or instead of theseexamples. For example, a sound sensor can incorporate microphone 226together with associated circuitry and/or program code to determine,e.g., a decibel level of ambient sound. Temperature sensors, proximitysensors, ambient light sensors, or the like can also be included.

Strap sensors 216 can include various electronic, mechanical,electromechanical, optical, or other devices that provide information asto whether wearable device 200 is currently being worn. For instance,clasp sensor 250 can be at least partially disposed within either orboth of clasp members 108 a, 108 b of FIG. 1 and can detect when claspmembers 108 a, 108 b are engaged with each other or disengaged from eachother. For example. engaging clasp members 108 a, 108 b to each othercan complete an electrical circuit, allowing current to flow throughclasp sensor 250; disengaging clasp members 108 a, 108 b from each othercan break the circuit. As another example, one or more contact sensors252 can be disposed in straps 106 a, 106 b and can detect contact with auser's skin, e.g., based on capacitive sensing, galvanic skin response,or the like. Contact sensors 252 can also include pressure sensors(e.g., piezoelectric devices) or the like. Any other type of sensor thatindicates whether wearable device 200 is currently being worn can beused in addition to or instead of strap sensors 216. For instance,physiological or biometric sensors, such as pulse sensors, ECG sensors,or the like can be provided. In some embodiments, physiological orbiometric sensors can be used in verifying the identity of the wearer ofwearable device 200.

Power subsystem 212 can provide power and power management capabilitiesfor wearable device 200. For example, power subsystem 212 can include abattery 240 (e.g., a rechargeable battery) and associated circuitry todistribute power from battery 240 to other components of wearable device200 that require electrical power. In some embodiments, power subsystem212 can also include circuitry operable to charge battery 240, e.g.,when connector interface 210 is connected to a power source. In someembodiments, power subsystem 212 can include a “wireless” charger, suchas an inductive charger, to charge battery 240 without relying onconnector interface 210. In some embodiments, power subsystem 212 canalso include other power sources, such as a solar cell, in addition toor instead of battery 240.

In some embodiments, power subsystem 212 can control power distributionto components within wearable device 200 to manage power consumptionefficiently. For example, power subsystem 212 can automatically placedevice 200 into a “hibernation” state when strap sensors 216 indicatethat device 200 is not being worn. The hibernation state can be designedto reduce power consumption; accordingly, user interface 206 (orcomponents thereof), RF interface 208, connector interface 210, and/orenvironmental sensors 214 can be powered down (e.g., to a low-powerstate or turned off entirely), while strap sensors 216 are powered up(either continuously or at intervals) to detect when a user puts onwearable device 200. As another example, in some embodiments, whilewearable device 200 is being worn, power subsystem 212 can turn display220 and/or other components on or off depending on motion and/ororientation of wearable device 200 detected by environmental sensors214. For instance, if wearable device 200 is designed to be worn on auser's wrist, power subsystem 212 can detect raising and rolling of auser's wrist, as is typically associated with looking at a wristwatch,based on information provided by accelerometer 242. In response to thisdetected motion, power subsystem 212 can automatically turn display 220and/or touch sensor 228 on; similarly, power subsystem 212 canautomatically turn display 220 and/or touch sensor 228 off in responseto detecting that user's wrist has returned to a neutral position (e.g.,hanging down).

Power subsystem 212 can also provide other power managementcapabilities, such as regulating power consumption of other componentsof wearable device 200 based on the source and amount of availablepower, monitoring stored power in battery 240, generating user alerts ifthe stored power drops below a minimum level, and so on.

In some embodiments, control functions of power subsystem 212 can beimplemented using programmable or controllable circuits operating inresponse to control signals generated by processing subsystem 202 inresponse to program code executing thereon, or as a separatemicroprocessor or microcontroller.

It will be appreciated that wearable device 200 is illustrative and thatvariations and modifications are possible. For example, strap sensors216 can be omitted, and wearable device 200 can include a user-operablecontrol (e.g., a button or switch) that the user can operate to indicatewhen wearable device 200 is being worn. Controls can also be provided,e.g., to turn on or off display 220, mute or unmute sounds from speakers222, etc. In some embodiments, other environmental sensors (e.g.,accelerometer 242) can be used to determine whether wearable device 200is being worn, in addition to or instead of strap sensors 216. Wearabledevice 200 can include any types and combination of sensors and in someinstances can include multiple sensors of a given type.

In various embodiments, a user interface can include any combination ofany or all of the components described above, as well as othercomponents not expressly described.

For example, in some embodiments, the user interface can include, e.g.,just a touchscreen, or a touchscreen and a speaker, or a touchscreen anda haptic device. Where the wearable device has an RF interface, aconnector interface can be omitted, and all communication between thewearable device and other devices can be conducted using wirelesscommunication protocols. A wired power connection, e.g., for charging abattery of the wearable device, can be provided separately from any dataconnection.

Further, while the wearable device is described with reference toparticular blocks, it is to be understood that these blocks are definedfor convenience of description and are not intended to imply aparticular physical arrangement of component parts. Further, the blocksneed not correspond to physically distinct components. Blocks can beconfigured to perform various operations, e.g., by programming aprocessor or providing appropriate control circuitry, and various blocksmight or might not be reconfigurable depending on how the initialconfiguration is obtained. Embodiments of the present invention can berealized in a variety of apparatus including electronic devicesimplemented using any combination of circuitry and software.

A host device such as host device 102 of FIG. 1 can be implemented as anelectronic device using blocks similar to those described above (e.g.,processors, storage media, user interface devices, data communicationinterfaces, etc.) and/or other blocks or components. Those skilled inthe art will recognize that any electronic device capable ofcommunicating with a particular wearable device can act as a host devicewith respect to that wearable device.

Communication between a host device and a wireless device can beimplemented according to any communication protocol (or combination ofprotocols) that both devices are programmed or otherwise configured touse. In some instances, standard protocols such as Bluetooth protocolscan be used. In some instances, a custom message format and syntax(including, e.g., a set of rules for interpreting particular bytes orsequences of bytes in a digital data transmission) can be defined, andmessages can be transmitted using standard serial protocols such as avirtual serial port defined in certain Bluetooth standards. Embodimentsof the invention are not limited to particular protocols, and thoseskilled in the art with access to the present teachings will recognizethat numerous protocols can be used.

In some embodiments, wearable device 200 can detect a transition from an“idle” position to an “active” position. For example, FIGS. 3A and 3Billustrate a user 300 wearing wearable device 302, which in this exampleis a wrist-worn device. As shown in FIG. 3A, when user 300 is notactively using wearable device 302, the user's arm 304 may hangnaturally at his side. To begin using wearable device 302, user 300 canrotate his arm to the position 304′ shown in FIG. 3B, raising the elbowto bring wearable device 302 into his line of sight. Dashed line 306indicates an approximate motion path of wearable device 302. Motionsensors (e.g., accelerometer 242 and/or gyroscopic sensor 246) candetect a characteristic motion associated with bringing wearable device302 into the user's line of sight; upon detecting this motion, wearabledevice 302 can automatically prepare itself to be used, e.g., byactivating user interface components such as display 220 and/or touchsensor 228. Other patterns of motion can also be detected and cantrigger activation of user interface components; for example, shaking ofthe wrist or a specific motion pattern of the arm or hand (e.g., movingin an “S” curve or circle or triangle). In some embodiments, wearabledevice 302 (or other wearable devices described herein) can have abutton (e.g., on the side of face 104 in FIG. 1) that a user can toggleto turn on or off a touchscreen interface; the button can be provided inaddition to or instead of motion-based detection of activation.

Referring again to FIG. 1, in some embodiments, host device 102 can sendvarious event notifications to wearable device 100, and the user canrespond to the notifications via wearable device 100. For example, hostdevice 102 can alert wearable device 100 to incoming communications suchas phone calls, text messages, voicemail messages, email messages, andthe like; upcoming meetings or events; stock market events such aschange in price of a particular stock; location-based reminders; and/orany other event that can be identified by host device 102. In someembodiments, the user may be able to select which types of events shouldgenerate notifications to wearable device 102, e.g., by interacting witha settings menu provided on host device 102.

FIG. 4 is a flow diagram of a process 400 for responding to an eventnotification according to an embodiment of the present invention.Process 400 can be implemented in a wearable device, e.g., wearabledevice 100 of FIG. 1 or wearable device 200 of FIG. 2, which can beinteracting with host device 102. In some embodiments, theimplementation of process 400 can include program code executed by aprocessor of wearable device 100.

At block 402, wearable device 100 can pair with a host device, e.g.,host device 102. For example, standard Bluetooth pairing techniques canbe used; other techniques for establishing a wireless connection betweentwo devices can be used. In some embodiments, an initial pairing betweentwo devices may involve user interaction with one or both devices toconfirm that the pairing should be established. Once the initial pairingis established, the two devices can automatically reconnect to eachother (without further user intervention) any time they come withincommunication range and are operating their respective RF transceivers.

At block 404, wearable device 100 can receive an event notification fromhost device 102. For example, host device 102 can send a notificationindicating an incoming phone call, text message, or email message. Atblock 406, wearable device 100 can present an alert to the user and canprompt the user for a response. The alert can include, e.g., an audiblealert, a vibration, a visual alert, or any combination of multiplealerts. The prompt can include, e.g., a visual prompt on display 220, anaudio prompt (e.g., a voice prompt), or the like.

FIG. 5 illustrates an alert-and-prompt screen 500 that can be displayedat block 406 when the event notification corresponds to an incomingphone call. Screen 500 can show an identifier of the caller 502; theidentifier can be determined by host device 102 (e.g., based on acontacts list stored therein and/or caller identifying informationreceived by host device 102) and sent to wearable device 100 as part ofthe event notification. Screen 500 can also prompt the user to respondto the call, e.g., by selecting virtual button 504 to instruct the phoneto answer the call, virtual button 506 to instruct the phone to placethe caller on hold, virtual button 508 to instruct the phone to divertthe call to voicemail, and virtual button 510 to decline the call. Otheralerts and prompts can be used, depending on the type of event,available response options, screen size of the wearable device, userpreferences, and similar design considerations.

In some embodiments, a sequence of screens can be presented as part ofprompting the user for a response. For example, FIG. 6 illustrates aprompt screen 600 that can be displayed at block 406 of process 400 whenthe event notification corresponds to an incoming text message. Screen600 shows an identifier of the sender of the text 602; as with a phonecaller, the identifier of a sender of a text can be determined by hostdevice 102 (e.g., based on a contacts list stored therein and/or sourceidentifying information received by host device 102). Screen 600 canalso show a preview of the text message 604; in some embodiments, theuser can scroll (e.g., by sliding a finger up or down on a touchscreen)to view more message content. Screen 600 can also prompt the user torespond to the text, e.g., by selecting virtual button 606 to reply tothe text or virtual button 608 to exit from screen 600 withoutresponding.

If the user selects virtual button 606, a message selection screen 700as shown in FIG. 7 can be displayed, providing a menu of predefined textmessages from which the user can select. For example, virtual button 702can be selected to send a “yes” message, virtual button 704 can beselected to send a “no” message; virtual button 706 can be selected tosend a “thanks” message; and virtual button 708 can be selected to senda “later” message indicating that the user will contact the senderlater. It is to be understood that buttons 702, 704, 706, 708 may notcontain the full text message to be sent but rather a short identifier.For example, the “no” identifier on button 704 can be associated with aless terse message such as “No, sorry,” and the “later” identifier onbutton 708 can be associated with a more specific message such as “I'llcall you later.”

Referring again to FIG. 4, at block 408, wearable device 100 can receivea user input in response to the prompt. For example, the user can selectvirtual buttons via one or more of screens 500, 600, or 700, dependingon context and what the user desires to do. At block 410, wearabledevice 100 can transmit a response message to the host based on thereceived user input.

It is not required that a user actually respond to any particular alerton wearable device 100. For example, in some embodiments process 400 cansimply time out and end at block 408 if the user does not provide inputwithin some fixed time period (e.g., 1 minute, 2 minutes, 5 minutes);the time period can be different for different types of events. Asanother example, a user can select the “close” option (button 608) froma screen such as screen 600, and this can be interpreted by wearabledevice 100 as an indication that the user does not intend to respond. Insome instances, a user may instead choose to respond to an alert byusing host device 102 directly; in such cases, host device 102 cannotify wearable device 100 if a response is received directly at hostdevice 102.

FIG. 8 is a flow diagram of a process 800 for generating an eventnotification and receiving a response according to an embodiment of thepresent invention. Process 800 can be implemented in a host device,e.g., host device 102 of FIG. 1, which can be interacting with awearable device 100 that executes process 400 of FIG. 4 or similarprocesses. In some embodiments, the implementation of process 800 caninclude program code executed by a processor of host device 102.

At block 802, host device 102 can detect an event that triggers a useralert, such as an incoming call or text message. At block 804, hostdevice 102 can determine whether a wearable device (e.g., wearabledevice 100) is currently paired. If not, then at block 806, host device102 can wait for a user input at its local interface to determinewhether and how the user chooses to respond.

If wearable device 100 is currently paired, then at block 808, hostdevice 102 can send an event notification to wearable device 100. Anycommunication protocol can be used, including standard Bluetoothmessages (e.g., incoming call alert), a message that conforms to acustomized serial protocol that can be transmitted using Bluetooth'svirtual serial port capability, or messages conforming to otherprotocols that are mutually understood by the host device and thewearable device. The notification can include information identifyingthe type of event (e.g., incoming phone call, text message received,stock market alert, etc.) and additional details specific to the event(e.g., name or other identifier of the caller, content of a textmessage, etc.).

At block 810, host device 102 can wait for a response, which can comefrom either the wearable device or a local user interface of host device102. For example, a user may receive an alert of an incoming call onwearable device 100 but choose to answer the call using host device 102.Accordingly, host device 102 can monitor activity on the connection towearable device 100 to detect a response and at the same time present alocal interface (e.g., on its own touchscreen display) and monitor thatinterface to detect a response.

At block 812, host device 102 can process the received response,regardless of whether it was received from wearable device 100 or via alocal user interface of host device 102. For example, referring to FIG.5, if a user selects one of virtual buttons 504, 506, 508, 510 fromscreen 500 on wearable device 100, host device 102 can receive aresponse from wearable device 100 indicating which button was selected.In response to answer button 504 being selected, host device 102 cananswer the call; call audio can be routed to wearable device 100 or toanother audio input/output device, such as an internal audio interfaceof host device 102 or a wireless headset that is paired with orotherwise in communication with host device 102. In response to holdbutton 506 being selected, host device 102 can answer the call and playa message to the caller indicating that the caller should hold. The usercan later take the call off hold, e.g., via a local user interface ofhost device 102 or via wearable device 100, allowing the user to speakwith the caller. In response to voicemail button 508 being selected,host device 102 can redirect the call to a voicemail account associatedwith the user, allowing the caller to leave a message. In response todecline button 510 being selected, host device 102 can reject orterminate the call.

As another example, referring to FIG. 7, if a user selects to reply to atext message with a predefined response, e.g., by selecting one ofbuttons 702, 704, 706, 708 on screen 700, host device 102 can generateand send the corresponding text message back to the sender. In someembodiments, wearable device 100 may provide an index or other shortname as an identifier for the text message. Host device 102 can maintaina lookup table or other data structure that maps the identifier to theactual message to be sent (e.g., a short-name identifier such as “later”or an index such as “3” can be mapped to “I'll call you later,” which isthe message that would be sent). In some embodiments, a user can definea set of text messages to be included in the predefined list byinteracting with host device 102, and host device 102 can provide shortnames and/or other identifiers for the user-defined messages to wearabledevice 100, e.g., in a synchronization operation.

It is not required that a user actually respond to a particular alert,either locally on host device 102 or via wearable device 100. In someinstances, process 800 can allow the alert to time out after a specificperiod (e.g., 1 minute, 2 minutes, 5 minutes) if the user does notrespond, in which case process 800 can end at block 806 or 810. Forexample, if an incoming call is not answered within the specified timeperiod after generating the alert, host device 102 can take a defaultaction such as diverting the call to a voicemail system. In someembodiments, if the user does not respond within the specified timeperiod, host device 102 can discontinue the alert and/or replace thealert with an informational notice that is visible to the user (e.g., amissed-call notification or the like).

It will be appreciated that processes 400 and 800 are illustrative andthat variations and modifications are possible. Steps described assequential may be executed in parallel, order of steps may be varied,and steps may be modified, combined, added or omitted. For instance, insome embodiments, a host device can present a user alert via its ownlocal interface in addition to sending a notification to a wearabledevice; in some embodiments, the host device presents a user alert viaits own local user interface only when the wearable device is notpaired; and in some embodiments, the user can specify whether the hostshould send a particular notification to the wearable device, present analert locally, do both, or do neither. A user alert on a host device ora wearable device can take the form of any sensory input detectable by ahuman and can include visual alerts (e.g., lights; displayed text, iconsand or images), audible alerts (e.g., tones, buzzes, ringtones, musicalsounds, and/or speech sounds), and/or tactile alerts (e.g., avibration).

The particular response options described above, e.g., with reference toFIGS. 5-7, are also illustrative, and the user may have other optionsfor responding to a given alert. Further, while processes 400 and 800have been described with reference to specific types of events (incomingcall, incoming text message), it is to be understood that notificationsof other types of events can be processed in the same manner. For anytype of event, the user can have the option to select one of a set ofresponses (which may be limited) via the wearable device's userinterface or to use the host device's local user interface to respond.In some instances, the host device's interface can offer a larger ordifferent range of possible response options than the wearable device(e.g., composing an arbitrary message as opposed to selecting from afinite set of predefined messages).

In some embodiments, in addition to or instead of responding to an eventon the host device, a user can use a wearable device to initiate afunctionality of the host device, e.g., placing a phone call, sending atext message that is not in response to a received text message, orinitiating any other functionality that is available on a particularhost device. FIG. 9 is a flow diagram of a process 900 for initiating aphone-call functionality of a host device according to an embodiment ofthe present invention. Process 900 can be implemented in a wearabledevice, e.g., wearable device 100 of FIG. 1 or wearable device 200 ofFIG. 2, which can be interacting with a host device 102 that provides atelephone transceiver capable of communicating over a phone network(e.g., a cellular telephony network, voice-over-IP system, or the like).In some embodiments, the implementation of process 900 can includeprogram code executed by a processor of wearable device 100.

At block 902, a user can select an option to place a call using the userinterface of wearable device 100. For example, referring to FIG. 10, auser interface of wearable device 100 can include a function selectionscreen 1000. Function selection screen 1000 can be a default screen thatappears when the display of wearable device 100 is activated or it canbe a different screen that the user can access through a touch gestureor sequence of gestures (e.g., to navigate through menus) on atouchscreen display, a hand or arm gesture detected by motion sensorsbuilt into wearable device 100, or other operations. Function selectionscreen 1000 can include various virtual buttons that the user can selectto invoke a functionality of host device 102, such as “call” button 1002to place a call, “text” button 1004 to send a text message, and “music”button 1006 to invoke a media player functionality of host device 102.In this example, a user can select an option to place a call byselecting button 1002.

Referring again to FIG. 9, at block 904, wearable device 100 candetermine whether it is currently paired with a host device 102 that iscapable of making phone calls. If not, wearable device 100 can alert theuser at block 906. The user can take corrective action, such as gettingwithin range of host device 102, turning host device 102 on, etc.

Assuming wearable device 100 is paired with a phone-capable host device102, then at block 908, wearable device 100 can present the user withcalling options, and at block 910, wearable device 100 can receive userinput selecting a calling option. For example, when a user selects callbutton 1002 of FIG. 10, an interface such as screen 1100 of FIG. 11 maybe displayed. FIG. 11 shows options for placing a call, such as anemergency call button 1102 that can be programmed to place a call to aphone number associated with an emergency service (such as 911 in theUnited States or 112 in many European countries), a keypad button 1104to allow a user to dial a number, and a contacts button 1106 to allow auser to look up a contact.

If the user selects keypad button 1104, wearable device 100 can presenta keypad interface, such as screen 1200 of FIG. 12. Screen 1200 includesa virtual phone keypad 1202 (e.g., a standard phone keypad with digits0-9 and “star” and “pound” keys) and a number box 1204 to show thedigits entered so far. In some embodiments, other controls can beprovided (e.g., back, cancel, and done buttons); in some embodiments,gestures can be associated with various control functions such aserasing a digit, canceling the operation, or indicating that entry ofthe number is complete. A user can operate keypad interface screen 1200to dial an arbitrary number.

If, from screen 1100 of FIG. 11, the user chooses contacts button 1106,wearable device 100 can present a selectable contacts list, such asscreen 1300 of FIG. 13. Screen 1300 can present the names of some or allof a user's contacts, e.g., as virtual buttons 1302, 1304, 1306, 1308.If the number of contacts exceeds the available space on screen 1300,the list can be scrollable (e.g., using upward or downward gestures on atouchscreen) to allow the user to view and select from any number ofcontacts.

Wearable device 100 can maintain various amounts of contact information.For example, wearable device 100 can maintain a list of names of theuser's contacts, which it can obtain, e.g., via synchronizationoperations with host device 102 or with other devices. Wearable device100 can maintain just the name and/or other information about eachcontact (e.g., phone numbers, photos) as desired. In some embodiments, auser can designate a subset of her contacts to be synchronized withwearable device 100, and host device 102 can have a larger list ofcontacts than wearable device 100 as well as more information about eachcontact. Alternatively, wearable device 100 can obtain contactinformation from host device 102 in real time, e.g., with user-definedfavorite contacts or most-recently-contacted contacts being presentedfirst and various options to retrieve additional contacts. Accordingly,a user can operate wearable device 100 to select a contact to be called.

Referring again to FIG. 9, once the user input that determines a numberto be called has been received (block 910), process 900 can send a callinstruction to host device 102 at block 912 to instruct host device 102to place the call. In some instances, e.g., where keypad screen 1200 wasused, the call instruction can include a phone number. In someinstances, e.g., where contacts screen 1300 was used to select the partyto be called, the call instruction can include the selected contact'sname (or other unique identifier), from which host device 102 candetermine the phone number to be called, e.g., by looking up theinformation in a user's contact list. Host device 102 can place thecall, and at block 914, wearable device 100 can receive confirmationthat the call has been placed. This confirmation can indicate whetherthe call connected, or it can be sent before the call is actuallyconnected.

At block 916, wearable device 100 can receive and send call-relatedaudio signals, allowing the user to communicate with the caller.Call-related audio signals can include input audio signals (e.g., speechof the user picked up by a microphone and delivered to the host devicefor transmission via the phone network) and/or output audio signals(e.g., speech of the other caller received at the host device via thephone network and delivered to a speaker). In some instances, outputand/or input audio signals can be sent to and/or received from abuilt-in speaker and/or microphone of wearable device 100. In otherinstances, wearable device 100 can send output audio to and/or receiveinput audio from external devices such as a wired or wireless headset.It is not required that all call-related audio signals, or indeed anycall-related audio signals, be routed through wearable device 100. Forexample, host device 102 can route input (or output) audio to (or from)a device other than wearable device 100 while using wearable device 100to route the output (or input) audio, and wearable device 100 canprocess the portion of audio for which it is in the routing path. Insome instances, all call-related audio signals can be routed to and fromdevices other than wearable device 100, in which case wearable device100 would not receive or send call-related audio signals but may simplywait until the call is completed. In some embodiments, wearable device100 can make other functions available to the user while a call is inprogress.

In some embodiments, while a call is in progress, wearable device 100can display a control operable by the user to end the call. At block918, if this control is operated, then at block 920, wearable device 100can alert host device 102 that the call should be ended. Host device 102can terminate the call and return a confirmation to wearable device 100at block 922. Wearable device 100 can present an alert to the user atblock 924 to confirm that the call has ended.

Host device 102 can also detect a call-termination event not originatingfrom wearable device 100, e.g., if the other party disconnects or if theconnection is dropped by the phone network. If this occurs, host device102 can send an event notification to wearable device 100. Accordingly,if the user does not end the call at block 918, then at block 926,wearable device 100 can determine whether host device 102 has sent acall termination notification. If so, then wearable device 100 can alertthe user at block 924. Otherwise, the call can continue (block 1408)until either the user terminates it or the host detects a terminationevent.

FIG. 14 is a flow diagram of a process 1400 for placing a call using awearable device according to an embodiment of the present invention.Process 1400 can be implemented in a host device, e.g., host device 102of FIG. 1, which can be interacting with a wearable device 100 thatexecutes process 900 of FIG. 9 or similar processes, and host device 102can provide a telephone transceiver capable of communicating over aphone network (e.g., a cellular telephony network, voice-over-IP system,or the like) In some embodiments, the implementation of process 1400 caninclude program code executed by a processor of host device 102.

At block 1402, host device 102 can receive a call instruction from apaired wearable device 100 that instructs host device 102 to place aphone call. The call instruction can include, e.g., a phone number to becalled or an identifier of a contact. At block 1404, host device 102 canplace the call. In some embodiments, placing the call can include usingthe contact identifier received at block 1402 to look up a correspondingphone number. At block 1406, host device 102 can send a confirmationthat the call has been placed. The confirmation can be sent, e.g., whilethe call is still being connected.

At block 1408, host device 102 can route the call-related audio signals(including input and output audio signals as described above withreference to FIG. 9) to and from appropriate input and output devices.Audio input and output devices can include an internal microphone orspeaker of host device 102 and/or an external microphone or speakerconnected to host device 102 by wired or wireless connections, includingin some instances wearable device 100. In some embodiments, host device102 can determine the routing based on what other devices are currentlyconnected to host device 102 and/or user-specified preferences regardingaudio routing. Accordingly, call-related audio can be routed to wearabledevice 100 or to another device. In some instances, input and outputaudio can be routed differently; for example, host device 102 canreceive input audio from wearable device 102 while providing outputaudio to a different device.

At block 1410, host device 102 can determine whether wearable device 102has sent a message indicating that the call should end. If so, then hostdevice 102 can end the call at block 1412 and send confirmation towearable device 100 at block 1414.

If, at block 1410, wearable device 102 has not indicated that the callshould end, then at block 1416, host device 100 can determine whether ithas received notification via the phone network that the call has ended(e.g., that the other endpoint has terminated the call or that theconnection has been dropped). In addition, in some embodiments, a userwho operated wearable device 102 to place a particular call can operatethe user interface of host device 100 to end the call. If host device102 detects any of these call-ending events, then host device 100 cannotify wearable device 102 that the call has ended at block 1418. Insome embodiments, the notification at block 1418 can include anindication of how the call ended (e.g., terminated by the otherendpoint, dropped call, etc.).

If, at block 1416, host device 100 does not detect that the call hasended, then process 1400 can return to block 1408 to continue to routeaudio for the call. Accordingly, the call can continue until it isterminated by either party.

Similar processes can be used to send other types of communication, suchas text messaging. For example, FIG. 15 is a flow diagram of a process1500 for sending a text message using a wearable device, e.g., wearabledevice 100 of FIG. 1 or wearable device 200 of FIG. 2, which can beinteracting with a host device 102 that provides a telecommunicationinterface capable of communicating text messages over a network (e.g., acellular telephony network, cellular data network, the Internet, or thelike) In some embodiments, the implementation of process 1500 caninclude program code executed by a processor of wearable device 100.

At block 1502, a user can select an option to send a text message, e.g.,by selecting text button 1004 from interface screen 1000 of FIG. 10. Atblock 1504, wearable device 100 can determine whether it is currentlypaired with a host device 102 that is capable of making phone calls. Ifnot, wearable device 100 can alert the user at block 1506. The user cantake corrective action, such as getting within range of host device 102,turning host device 102 on, etc.

At block 1508, wearable device 100 can present the user with options forselecting a recipient, and at block 1510, wearable device 100 canreceive the user's selection. In some instances, interface screenssimilar to those shown in FIGS. 11-13 can be used. For example, the usercan send a text to an arbitrary phone number by entering the number intokeypad 1202 of screen 1200, or the user can select a contact from screen1300. In some embodiments, the same list of contacts can be used forboth calls and text messages; in other embodiments, a user can definedifferent lists of favorite contacts for different communication media.

At block 1512, wearable device 100 can present the user with options fortexts to send, and at block 1514, wearable device 100 can receive theuser's selection. For example, similarly to process 400 described above,a user can have a predefined list of texts to send, allowing the user toavoid entering the text character-by-character. FIG. 16 illustrates aninterface screen 1600 for selecting a predefined text message that canbe used at block 1512. The predefined text messages can be differentdepending on whether the user is initiating a new text message (as inprocess 1500) or responding to a received text message (as in process400). For example, button 1602 can be associated with a text such as“I'm leaving now” and button 1604 with a text such as “I'm runninglate,” which are examples of text messages that a user might send to aperson she is going to meet. Button 1606 can be associated with a textsuch as “Please call me,” which requests the recipient to take aparticular action. Button 1608 can be associated with a text such as “Doyou need anything from the grocery store?” which a user might send whileon the way to the store. Other options can be provided in addition to orinstead of these examples, and in some embodiments the user can definespecific text messages and short identifiers in a manner similar to thatdescribed above with reference to FIG. 7.

In some embodiments, wearable device 100 can provide an option to enteran arbitrary text using alphanumeric or other character systems. Forexample, each character in a character system can be mapped to adifferent touch gesture, and a user can enter text by making touchgestures on touchscreen display 105. As another example, each charactercan be mapped to a different sequence of taps (e.g., Morse code or thelike), and a user can enter text by tapping touchscreen display 105. Asyet another example, touchscreen display 105 can present a compactvirtual keypad in which a character is determined based on the keylocation and number of times the user taps the key.

At block 1516, wearable device 100 can instruct the host device to sendthe text message and can provide an identifier of the intended recipient(e.g., phone number or name) and an identifier of the text to be sent;the identifier can be, e.g., an index, a short identifier, or the actualtext entered or selected by the user. As in process 900 described above,host device 102 can use the recipient identifier to determine the phonenumber, and as in processes 400 and 800 described above, host device 102can use a short identifier of the text message to identify the actualmessage to be sent. In some embodiments, at block 1518, wearable device100 can receive a confirmation from host device 102 that the text wassent and/or received; if desired, wearable device 100 can present acorresponding alert or informational message to the user.

It will be appreciated that the communication-initiation processesdescribed above are illustrative and that variations and modificationsare possible. Steps described as sequential may be executed in parallel,order of steps may be varied, and steps may be modified, combined, addedor omitted. Messages can be sent using various communication media andformats, including text messages (sent, e.g., via a short messagingservice (SMS) provided by a cellular communication network that carriesvoice and/or data); email messages, instant messages, social-networkmessages (any of which can be sent, e.g., via an Internet interface ofthe host device); and other types of messages.

In some embodiments, a user can define “quick-access” actions, such as“call Mom” or “text Bob that I'm running late” that can be executed witha reduced number of input actions (e.g., a single gesture to bring up aquick-access list, followed by tapping on the appropriate entry). Thiscan facilitate communication by and with users who are in the midst ofother activities and find it inconvenient to locate their phone to senda quick message or place a call.

Control over host device functions is not limited to communicationfunctions. For example, in some embodiments, a host device 102 can havemedia player capabilities, allowing a user to select and play mediatracks (e.g., audio and/or video), and wearable device 100 can provideremote control over media playback operations of a host device.

Referring again to FIG. 10, interface screen 1000 for wearable device100 includes a button 1006 that can be selected to control mediaplayback in a host device. In some embodiments, in response to userselection of button 1006, wearable device 100 can present an interfaceto select and control media player functions of host device 102. Forexample, wearable device 100 can display lists of playlists, albums,artists, genres, or songs from which the user can select tracks to play;once a track is playing, wearable device 100 can provide playbackcontrols such as play, pause, skip to previous or next track, rewind,fast-forward, volume control and the like, and the user can controlplayback using touch gestures on the display device.

In addition or instead, control can be provided based on movement ofwearable device 100 itself. For example, accelerometers, gyroscopes, orthe like can be used to detect motion of wearable device 100, andcertain motions can be defined as spatial gestures, which in turn can beinterpreted as controls. Thus, in some embodiments, a user can controlthe volume, e.g., by circling her wrist or arm clockwise to increase andcounterclockwise to lower. Other gestures can be associated with otheractions, e.g., a quick up-and-down to play, a quick down-and-up topause, quick right-then-left to skip ahead, quick left-then-right toskip back, etc. Different gestures can be associated with differentcontrol operations as desired.

It is to be understood that other devices can be controlled by awearable device. For example, a wearable device can provide control overenvironmental systems (e.g., heating, lights) through an appropriateuser interface.

While the invention has been described with respect to specificembodiments, one skilled in the art will recognize that numerousmodifications are possible and that components, operations, and/or otherfeatures that may be described with respect to different embodiments canbe incorporated into the same embodiment. Wearable devices can interactwith host devices to facilitate a variety of operations with increasedconvenience to the user.

All user interfaces shown herein are also illustrative. Sizes of userinterfaces or graphical elements thereof can be modified according to aparticular desired form factor of a wearable device and/or host device.Icons can be used in addition to or instead of text to identifyassociated functions, and the number and arrangement of controls can bevaried to facilitate user operation. In some embodiments, the user maybe able to scroll the display, e.g., by dragging one or two fingersalong the surface of a touchscreen display to see more options than canbe presented at once. Further, while the foregoing description may referto graphical user interfaces, other interfaces can also be used. Forexample, an audio input interface can be provided by allowing the userto speak into a microphone of a wearable device; the wearable device caninterpret the audio signal locally to determine a correspondinginstruction or send the audio to a host device for interpretation.Similarly, an audio output interface can be provided by using a speakeron the wearable device to produce sounds. The sounds can include tones(beeps, whirrs, etc.) and/or speech sounds; for example, synthesizedspeech can be generated on a host device and transmitted to the wearabledevice as a digital audio signal, or the wearable device can include itsown speech synthesizer. In some embodiments where a wearable device isworn on the user's hand, wrist, or arm, user input can include spatialgestures with the hand, wrist, and/or arm that are detected using motionsensors of the wearable device in addition to or instead of touchgestures involving contact with a touch-sensitive surface of thewearable device. Different gestures can be assigned different meanings,and the meaning of a gesture can be context-dependent, e.g., dependingon what operations of the host device and/or wearable device arecurrently in progress. Thus, the same gesture can, in differentcontexts, indicate hanging up a call or stopping playback of a mediatrack. Touch gestures and spatial gestures can be used in variouscombinations as desired.

The foregoing description may make reference to specific examples of awearable device (e.g., a wrist-worn device) and/or a host device (e.g.,a smart phone). It is to be understood that these examples areillustrative and not limiting; other devices can be substituted and canimplement similar functional blocks and/or algorithms to performoperations described herein and/or other operations.

Embodiments of the present invention, e.g., in methods, apparatus,computer-readable media and the like, can be realized using anycombination of dedicated components and/or programmable processorsand/or other programmable devices. The various processes describedherein can be implemented on the same processor or different processorsin any combination. Where components are described as being configuredto perform certain operations, such configuration can be accomplished,e.g., by designing electronic circuits to perform the operation, byprogramming programmable electronic circuits (such as microprocessors)to perform the operation, or any combination thereof. Further, while theembodiments described above may make reference to specific hardware andsoftware components, those skilled in the art will appreciate thatdifferent combinations of hardware and/or software components may alsobe used and that particular operations described as being implemented inhardware might also be implemented in software or vice versa.

Computer programs incorporating various features of the presentinvention may be encoded and stored on various computer readable storagemedia; suitable media include magnetic disk or tape, optical storagemedia such as compact disk (CD) or DVD (digital versatile disk), flashmemory, and other non-transitory media. Computer readable media encodedwith the program code may be packaged with a compatible electronicdevice, or the program code may be provided separately from electronicdevices (e.g., via Internet download or as a separately packagedcomputer-readable storage medium).

Thus, although the invention has been described with respect to specificembodiments, it will be appreciated that the invention is intended tocover all modifications and equivalents within the scope of thefollowing claims.

What is claimed is:
 1. A wearable device, comprising: a memoryconfigured to store computer-executable instructions; a touch-screendisplay; and a processor configured to access the memory and execute thecomputer-executable instructions to at least: detect that the wearabledevice is being worn by a user; while the wearable device is in a firstposition with respect to the user: maintain a backlight of thetouch-screen display in an off-state; and determine, based at least inpart on sensor data from one or more sensors of the wearable device,that the wearable device has moved from the first position with respectto the user to a second position with respect to the user; and inaccordance with a determination that the wearable device has moved fromthe first position to the second position, transition the backlight ofthe touch-screen display of the wearable device to an on-state.
 2. Thewearable device of claim 1, wherein detecting that the wearable deviceis being worn by the user comprises receiving information, from at leasta second sensor, indicative that the wearable device is being worn. 3.The wearable device of claim 1, wherein the second position comprises alocation wherein the touch-screen display is viewable by the user. 4.The wearable device of claim 1, wherein the second position comprises alocation wherein the touch-screen display is oriented towards the user.5. The wearable device of claim 1, wherein the first position comprisesa location wherein the touch-screen display is not viewable by the user.6. The wearable device of claim 1, wherein the first position comprisesa location wherein the touch-screen display is oriented away from theuser.
 7. The wearable device of claim 1, wherein the one or more sensorscomprises at least an accelerometer sensor.
 8. The wearable device ofclaim 1, wherein the one or more sensors comprises at least a gyroscopesensor.
 9. A method of operating a wearable device, comprising: at adevice with one or more sensors and a touch-screen display: while thetouch-screen display is in an inactive state: detecting, with the one ormore sensors, a motion characteristic of a user moving the wearabledevice into a viewing position; and in response to detecting the motion,activating the touch-screen display.
 10. The method of claim 9, furthercomprising detecting, the one or more sensors of the wearable device,that the wearable device is being worn by the user, the motion beingdetected only if the wearable device is being worn.
 11. The method ofclaim 9, wherein the one or more sensors comprises at least anaccelerometer sensor.
 12. The method of claim 9, wherein the one or moresensors comprises at least a gyroscope sensor.
 13. The method of claim9, wherein the active position comprises a location wherein thetouch-screen display is oriented towards the user.
 14. The method ofclaim 9, wherein the wearable device is adapted to be worn on a user'swrist and wherein the motion characteristic of the user moving thewearable device into the viewing position corresponds to a wrist of theuser being moved into a line of sight.
 15. A wearable device,comprising: a memory configured to store computer-executableinstructions; a touch-screen display; and a processor configured toaccess the memory and execute the computer-executable instructions to atleast: detect that a user is wearing the wearable device; while thewearable device is in a first position with respect to the user:maintain a backlight of the touch-screen display in an off-state; anddetect an event that indicates that the user has moved the wearabledevice from a first position with respect to the user to a secondposition with respect to the user; and transition a backlight of thetouch-screen display of the wearable device to an on-state in accordancewith the event.
 16. The wearable device of claim 15, wherein the eventcomprises the wearable device being rotated, on an arm of the user, fromthe first position to the second position.
 17. The wearable device ofclaim 15, wherein the first position comprises a location wherein thetouch-screen display is not viewable by the user.
 18. The wearabledevice of claim 15, wherein the processor if further configured toexecute the computer-executable instructions to at least determine thatthe wearable device is being worn by the user.
 19. The wearable deviceof claim 18, wherein the processor if further configured to execute thecomputer-executable instructions to only transition the backlight of thetouchscreen to the on-state when the wearable device is being worn bythe user.
 20. The wearable device of claim 15, wherein the secondposition comprises a location wherein the touch-screen display is notviewable by the user.